DBM-6000 : Protocol Converter for the BIBUS CENTRAL (ANB)

This protocol has been validated on a DBM-6000 ARM controller with an IP protocol converter. Interfacing has been developed with a BiBus classic unit and a DuoTecno interface.

Detectors, partitions and others alarm's informations like sirens can be monitored. There is a possibility for the DBM-6000 to arm or disarm a specified partition.

To interface a BiBus central to the DBM-6000, one Protocol Converter and one DuoTecno rs-232 serial interface are needed.

A protocol converter can monitor up to 2000 points. This capacity is limited by the number of DinCool channels in the controller.

In the installation window, let us say that each item is a node.

1) How to set up the system
2) Configuration of the Converter node
3) Configuration of the Interface node
4) Configuration of the Messages node
5) Configuration of the Variables
6) Accessing variables with DinTalk
7) Connection control
8) Cabling RS-232
9) Screen examples

1) How to set up the system:

Add a protocol converter on the controller.
In the window “management of the devices on the main bus”, control that the model is "BIBUS 6000" and the version is "3.30". If it is not the case, then burn the converter flash with the file named BIBUS_IP.S24 .
Add a single slave (address 0) on the converter: the DuoTecno Interface.
Add the messages sets. Three messages can be defined. The first is for the Detectors (address 1), the second for the Partitions (address 2), the third for the Informations (address 3).
Add detectors in the first message (max 255), partitions in the second message (max 8) and the 7 informations fields to the third message. See below for details.
TIPS:
- To set up the system quickly and in a safe way, start with one detector, set it up completely and verify its correct function. For the following detectors, use all possibilities of COPY/INSERT and COPY/PASTE on whole messages: it will create all the detectors for you.
- To control and rename variables quickly, use the 'list variables' options from the protocol converter or the BiBus icon sub-menu.

2) Configuration of the Converter node:

Name	BiBus Converter	mandatory: a name to identify the protocol converter
Address	xxxx	mandatory: the serial number labelled on the protocol converter.
Protocol	Alarm Central	mandatory
Bauds	19200	mandatory
Bits	8	mandatory
Parity	None	mandatory
Number Retry	-	This is the number of times the message is repeated before the converter generates a fault on the bus. Not use here.
Rx Time out	-	This is the time interval before repeating a message not acknowledged. Not use here.
Rx Time Ready	-	This is the delay before sending the next message after an acknowledge. Not use here.

3) Configuration of the Interface node:

The DuoTecno rs-232 serial interface is the only slave for the Converter node.

Name	A denomination for the DuoTecno interface
Address	0
*Survey this connection*	Should be checked, or no alarm bus error will be generated.

4) Configuration of the Messages node:

A message can be a detectors group, a partitions group or some alarms informations. You can give a name at your convenience but the address must be 1-2-3.

*Name*	The message name
*Address*	The address of the message (must be as in the following capture)

5) Configuration of the Variables:

As seen before, the variables can be detectors, partitions or other alarms information.

When you create a variable, this configuration popup is automatically displayed.

Later, when editing a variable properties, go in the 'Installator' sheet and click on 'Input properties' or select the variable in the variable list that can be accessed by a right-click on the 'Interface node' or the 'Converter node' (menu is 'Display the grid with the variables').

As for any other DinCool channel, you can set alarms for detectors. In case of alarm, it is immediate unless you made a inhibition.

Detectors and partitions :

Name	the detector's name or the partition's name
Address	the detector's number (from 1 to 255) or partition's number (from 1 to 8)

Infos : the names can be modified at your convenience but the meaning is as follow :

Address	Name
1	External Siren
2	Internal Siren
3	Flash light
4	Sabotage
5	Fault
6	Loss of 220V
7	Technical mode

5.1 Channel properties:

States 0 to 1 are used. Set the following texts (or something at your best convenience but the meaning is) :

for Detectors:

0: Inactive

1: Active

for Partitions:

0: Disabled

1: Armed

for Infos:

0: Idle

1: Run

5.2 The default plan images :

	Not known
	Inactive
	Inactive

6) Accessing variables with DinTalk:

Add an external variable of type integer. Select the wanted channel in the list.

Possible integer values are 0 to 1 depending on the tag status.

Partitions can be armed or disabled by a PRINT command in DinTalk, the parameter after the address of the protocol converter is a string which must be in the format 'X Y' (with one space between X and Y) where :

X values are: 1 to arm a partition, 2 to disable a partition,

Y is the partition number between 0 and 7 (0 for partition 1, 7 for partition 8)

see sample DINTALK code below

7) Connection control:

Don't forget to set the 'Alarm on device offline' in the controllers properties.

If the protocol converter is disconnected, the converter detects the absence of communication and an error bus is generated immediately. The alarm programmed for main bus errors (if any) in the controller is started.

If the DuoTecno RS-232 module is disconnected from the converter, the converter detects the absence of communication and an error bus is generated. The alarm programmed for main bus errors (if any) in the controller is started.

8) Cabling RS-232

Wiring : RS-232 cable: 3 wires

Protocol converter (Modbus port)	RJ-11
RX (IN1)	1 (TX)
TX (IN2)	2 (RX)
GND	3 (GND)

See also the cabling diagrams in the general help of the DBM-6000.

9) Screen examples

In this example, only 8 detectors where defined, but you can add till 255 detectors. Partitions and Infos are fully defined.

DinTalk sample program :

Here you can find a sample program which do the following :

Arm or disable a partition from the plan. This will be achieved with 2 buttons by partition, one for arm (action on an array of boolean bSetPart[8]), one for disable (array of boolean bResetPart[8]).

Another boolean array (bOpenPart[8]) will be used to inhibit alarms on detectors (you must know in which partition are the detectors)

An array of boolean named bArmPart[8] is used for the current asked command

An array of Timers named TimerPart[8] is used to make a delay (6 seconds) when arming a partition before inhibition is released.

Variables Part1 to Part8 are 8 DinCool variables to know the current partition status.

Here is the code :

Plan sample :

This capture shows a simple plan of the installation with the buttons to arm or disable a partition :

Programmation of button 'Arm Part 1' :

simple click is : modify a variable
variable is : bSetPart[00]
action is : Set to '1'

Programmation of button 'Disable Part 1' :

simple click is : modify a variable
variable is : bResetPart[00]
action is : Set to '1'

Programmation of the LED for partition 1 :

Variable is : bOpenPart[00] (open means that the partition is not armed)
state ?: white led
state 0: green led
state 1: blue led

Programmation of the Detector :

Attach it to the right variable (Detector 1 à 255)
state ?: greyed color
state 0 : green color
state 1 : red color

To make the inhibition working :

go to the Detector configuration and set the inhibition with the variable corresponding to the partiton in which is installed the detector :

and don't forget to add an alarm in the 'Alarm signal' sheet